test(ci): cover the missing-tag path under STRICT - #314
Conversation
The strict set exercised three of the four bail() paths; STABLE_TAG was the one left dark.
|
Warning Review limit reached
Next review available in: 44 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Follow-up to #289, which merged before this landed.
CodeRabbit's nitpick on that PR was right: the strict set exercised three of the four
bail()paths — missing Discord config, failed channel lookup, failed post — and leftSTABLE_TAGdark. UnderSTRICTthat path callssetFailedand exits 1 like the others, but nothing pinned it.One test, asserting
setFailedreceives the missing-tag message. 13 tests, suite green.🤖 Generated with Claude Code